View Issue Details

IDProjectCategoryView StatusLast Update
0001806T99X171.00 SKB EagleSW Issuepublic2024-07-09 09:59
Reporter(ALTech) Younkwang Jung Assigned To(ALTech) JunGyu Kim Due Date
PriorityurgentSeveritys4-minorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0001806: [Smart3][UI537] An issue is observed that the resolution automatically changes during sleep/wakeup after setting the resolution
DescriptionHi Kerwin

Test FW : 15.537.60
An issue is observed that the resolution automatically changes during sleep/wakeup after setting the resolution.

Please try sleep/wakeup after changing the resolution.(1080 or 720p )
(It's easy to reproduce.)
1) Set the resolution to 720 or 1080.
2) Sleep/wake up.
3) Check the resolution at the TV.

I also attached a video.
Please check it

Thank you
YK.Jung
TagsNo tags attached.
Attach Tags

Users monitoring this issue

User List (ALTech) JunGyu Kim , (ALTech) SY Yoon

Activities

(ALTech) Younkwang Jung

2023-09-04 20:06

developer  

logcat.zip (806,241 bytes)

(ALTech) JunGyu Kim

2023-09-04 20:32

developer   ~0014074

Hi Kerwin,

We have tested v15.537.56 and this FW is not reproduce.
Please refer it.

Thank you.
Kim

(ALTech) JunGyu Kim

2023-09-04 20:38

developer   ~0014075

Hi Kerwin, Jason.

Additionally, We have tested v15.537.400 and the issue is reproduce.
https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1765#c13858
It seems this issue related fixed mode.

Please refer it.

Thank you.
Kim

(SW) Jason Ling

2023-09-04 21:17

developer   ~0014076

Hi JunGyu,

If you think this issue related to Fix Mode, I think we should check it with Amlogic,
Because our modification is very simple.
You can check https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1765#c13846, we only new the FIXED_SIZE_POLICY. The logic is the same as the original Fix mode.
And We didn't modify any Fixes mode's codes in HWC, it's original Fix mode's code.

if SPTEK needs any additional behavior in Fix mode, Please let us know, we will check BTF API.

Thanks,
Jason

(SW) Jason Ling

2023-09-04 21:40

developer   ~0014077

Hi JunGyu,

Could you also check it with Digicap?
During I tracing nonoverride property flow last month,
As I remember, HomeUI will set resolution when STB suspend/resume.

I check the logcat
09-04 20:48:19.547 4679 4679 D DisplayUtil: adjustDisplay() call | width : 1920 | height : 1080 | density : 320
09-04 20:48:19.547 4679 4679 I DisplayUtil: adjustDisplay() nonoverride is true

The adjustDisplay function is Digicap function that you describe in mantis 1806
https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1806
Did they set the resolution again ?
I feel weird, if the nonoverride is true, I didn't see the following log in the logcat
"adjustDisplay() not support current resolution" or "adjustDisplay() nonoverride is true return"

Thanks,
Jason
image-3.png (65,042 bytes)   
image-3.png (65,042 bytes)   

(SW) Jerry Lin

2023-09-05 16:17

developer   ~0014079

Hi JunGyu,
commit done!

commit 7e8924c307cdbe7becbd7e21ac22abd257f98793 (HEAD, skb/BFX-AT100_5.3.7, m/BFX-AT100_5.3.7)
Author: jerry <liang-chyi.lin@fii-foxconn.com>
Date: Tue Sep 5 16:03:20 2023 +0800

    [BPM-22284] Revert "corrected the method of HDMI enable/disable control"

    This reverts commit a06bc60c4f826f7e4c1f069aecfebb6023c39180.

Jerry

(ALTech) Younkwang Jung

2023-09-07 18:01

developer   ~0014108

Last edited: 2023-09-07 18:03

View 2 revisions

Hi Jerry

After applying the above patch, LG TV is observing the problem.

please check attached video and log file

and please review whether it is related to the code you committed
( Additionally, no issue is observed when HDCP is disabled )

Thank you
YK.Jung

(ALTech) JunGyu Kim

2023-09-07 19:42

developer   ~0014109

Hi Jerry,

I also attached kernel log when the issue reproducing.

========================================================
[Thu Sep 7 15:47:04 2023] cectx ff80023c.aocec: type 4, save phy_addr:0x1000
[Thu Sep 7 15:47:05 2023] cectx ff80023c.aocec: cec a rx len 5:0f 87 00 e0 91
[Thu Sep 7 15:47:05 2023] cectx ff80023c.aocec: read msg len=5
[Thu Sep 7 15:47:05 2023] cectx ff80023c.aocec: type 4, save phy_addr:0x1000
[Thu Sep 7 15:47:05 2023] cectx ff80023c.aocec: read msg len=1
[Thu Sep 7 15:47:16 2023] hdmitx: hdmitx_set_uevent[224] hdmitx_hdcp=0 0
[Thu Sep 7 15:47:16 2023] hdmitx: hdcptx: 1 auth: 0
[Thu Sep 7 15:47:16 2023] hdmitx: hdcp14: instat: 0x41
[Thu Sep 7 15:47:16 2023] hdmitx: hdcp14: instat: 0xc1
[Thu Sep 7 15:47:16 2023] hdmitx: hdcp14: instat: 0x41
[Thu Sep 7 15:47:16 2023] hdmitx: hdmitx_set_uevent[224] hdmitx_hdcp=1 0
[Thu Sep 7 15:47:16 2023] hdmitx: hdcptx: 1 auth: 1
[Thu Sep 7 15:47:19 2023] cectx ff80023c.aocec: cec a rx len 5:0f 87 00 e0 91
[Thu Sep 7 15:47:19 2023] cectx ff80023c.aocec: read msg len=5
[Thu Sep 7 15:47:19 2023] cectx ff80023c.aocec: type 4, save phy_addr:0x1000
[Thu Sep 7 15:47:19 2023] cectx ff80023c.aocec: cec a rx len 5:0f 87 00 e0 91
[Thu Sep 7 15:47:19 2023] cectx ff80023c.aocec: read msg len=5
[Thu Sep 7 15:47:19 2023] cectx ff80023c.aocec: type 4, save phy_addr:0x1000
========================================================

When the issue was reproduced, hdcp auth was set to 0 -> 1
Please refer it.

Thank you.
Kim

(SW) Jerry Lin

2023-09-08 17:11

developer   ~0014112

Last edited: 2023-09-08 17:13

Hi YK,

1. The following code in DisplayMode.cpp is porting from ATV10.
/*
* OUPUT_MODE_STATE_SWITCH for UI set
*/
void DisplayMode::setSourceOutputMode(const char* outputmode) {
#ifndef RECOVERY_MODE
    AutoMutex _l( mLock );
#endif
+ setSourceOutputMode(outputmode, OUPUT_MODE_STATE_SWITCH);
+ return;

2. AML add many patches in function "void DisplayMode::setSourceOutputMode(const char* outputmode, output_mode_state state)" included set bestmode to false.

3. if we do not call this function , AML patches can not be execute.

Please help to confirm with AML if we restore my modified code from this function, how do we modify these patches to original AML code ?

Jerry

(SW) Jerry Lin

2023-09-08 17:46

developer   ~0014113

Last edited: 2023-09-08 21:23

Hi YK,
I can not reproduce this issue in my side.
I test 2160p60 HDR video by Youtube apk and DRM video by Exoplayer apk.
And also check WV/HDCP14/22 by Exoplayer apk.

Test FW : 15.537.64
TV: LG OLED55B7T

Jerry

(ALTech) Wooshin Kang

2023-09-11 10:16

developer   ~0014116

Hi jerry,

I can't understand why you had different result.
It is reproduced 100% ratio in my side.

Can you give a log to us ?

Thanks.

(SW) Jerry Lin

2023-09-11 10:24

developer   ~0014118

Hi Wooshin ,
My steps are same as the following:
1. Set 2160p60 in SKB UI.
2. Play Youtube 2160P60 video.

I wll give you YouTube log.
Is this okey?

Jerry

(ALTech) Wooshin Kang

2023-09-11 10:50

developer   ~0014119

Last edited: 2023-09-11 10:51

Hi Jerry,

Below is steps to reproduce.

1. Set 720P in SKB UI.
2. Return to Live channel
3. go standby mode, wait 30 secs
4. return to normal mode, and check resolution on TV.

Thanks.

(SW) Jerry Lin

2023-09-11 11:03

developer   ~0014121

Hi Wooshin,
This ticket has 2 issues.
1. An issue is observed that the resolution automatically changes during sleep/wakeup after setting the resolution. <== fixed in v64
2. please check with c14108 <=== Flicker issue with LG TV.

Jerry

(SW) Jerry Lin

2023-09-11 11:05

developer   ~0014122

Hi Wooshin,
please check with #c14112.

Jerry

(ALTech) Wooshin Kang

2023-09-11 11:42

developer   ~0014123

Hi jerry,

I am sorry for confusing you. Flicker issue come from reverting your patch.
And you can't see Flicker issue now.
Ok I understand.

Thanks,

(SW) Jason Ling

2023-09-11 12:13

developer   ~0014124

Hi YK, Wooshin,

Regarding current LG TV flicker issue (We can not reproduce it on our side)

YK has done some tests last week for LG TV flicker issue)

v15.537.60 ( No issue ): if (!strcmp(outputmode, "displayon") || !strcmp(outputmode, "displayoff")) { setSourceOutputMode(outputmode, OUPUT_MODE_STATE_SWITCH); return }
=> it make senses, because some "set resolution" flow was blocked, the code only allow displayon/displayoff to call function setSourceOutputMode( 2 parameters )

v15.537.64 ( Flicker issue ): setSourceOutputMode(outputmode, OUPUT_MODE_STATE_SWITCH);
v15.537.65 ( No issue ): setSourceOutputMode(outputmode, OUPUT_MODE_STATE_SWITCH); + revert AML patch (Systemcontrol: color space be changed after switch resolution [1/1])
=> It looks like some combination of patches can cause this issue.

Could you check set resolution flow with Amlogic?

In Android 10, the set resolution is as follows,
setSourceOutputMode(const char* outputmode) -> setSourceOutputMode(const char* outputmode, output_mode_state state)

And Amlogic added many pathes in setSourceOutputMode(2 parameters), Foxconn also added BTF API (supported displayon/dislayoff) in setSourceOutputMode(2 parameters)

From Android 12, in AML original SDK
setSourceOutputMode (1 parameter) didn't call setSourceOutputMode(2 parameter).
so Jerry porting this modification from Android 10.
- call the setSourceOutputMode(2 parameter) in setSourceOutputMode (1 parameter).

If Jerry didn't modify it. the modification that fixed in Andorid 10 by Amlogic before will not be executed.
For example: set best mode to false
you can grep "setBootEnv(UBOOTENV_ISBESTMODE, "false");", This line only appear in setSourceOutputMode (2 parameter)

Other place didn't set the best mode to false. if we restore to Amlogic original ATV12 SDK (doesn't call setSourceOutputMode (2 parameter)) , I think you will see the original issue (the resolution setting will gone after standby/resume).

Thanks,
Jason.

(SW) Jerry Lin

2023-09-11 15:25

developer   ~0014126

Last edited: 2023-09-11 15:26

Hi Mr. SY Yoon,
About this commit :
commit 7e8924c307cdbe7becbd7e21ac22abd257f98793 (HEAD, skb/BFX-AT100_5.3.7, m/BFX-AT100_5.3.7)
Author: jerry <liang-chyi.lin@fii-foxconn.com>
Date: Tue Sep 5 16:03:20 2023 +0800

    [BPM-22284] Revert "corrected the method of HDMI enable/disable control"

    This reverts commit a06bc60c4f826f7e4c1f069aecfebb6023c39180.


Previously we wanted to port ATV12 from ATV10, so we added this patch.
The main purpose is to use HAL API to control the TV to ON or OFF.
If it is not a command from HAL API , the original AML code will be executed.
However, it was found on R60 that the original AML code did not call "set best mode to false", so this issue happened.
And YK ask us to revert this patch first to ensure that the resolution setting can be completed through setSourceOutputMode().
You can refer #0014124. Jason has a more detailed description.

Jerry

(SW) Jerry Lin

2023-09-11 22:13

developer   ~0014130

Hi YK,
I add diff file.

Jerry
diff.patch (5,153 bytes)   
diff --git a/frameworks/services/systemcontrol/DisplayMode.cpp b/frameworks/services/systemcontrol/DisplayMode.cpp
index c18e6c74..42aa0adc 100644
--- a/frameworks/services/systemcontrol/DisplayMode.cpp
+++ b/frameworks/services/systemcontrol/DisplayMode.cpp
@@ -701,8 +701,34 @@ void DisplayMode::setSourceOutputMode(const char* outputmode) {
 #ifndef RECOVERY_MODE
     AutoMutex _l( mLock );
 #endif
-    setSourceOutputMode(outputmode, OUPUT_MODE_STATE_SWITCH);
-    return;
+    //Vas added to control HDMI output
+    if (!strcmp(outputmode, "displayon")) {
+        if (isDisplayOn == true) return;
+        pSysWrite->writeSysfs(DISPLAY_HDMI_STOP_HPD, "0");
+        isDisplayOn = true;
+        return;
+    } else if (!strcmp(outputmode, "displayoff")) {
+        if (isDisplayOn == false) return;
+        pSysWrite->writeSysfs(DISPLAY_HDMI_PHY, "0");
+        usleep(50000);
+        pSysWrite->writeSysfs(DISPLAY_HDMI_STOP_HPD, "1");
+        usleep(50000);
+        isDisplayOn = false;
+        return;
+    }
+
+    // When user switch outputmode, store bestmode
+    if (!strcmp(outputmode, "auto")) {
+        hdmi_data_t data;
+
+        SYS_LOGI("outputmode is [auto] mode, need find the best mode\n");
+        setBootEnv(UBOOTENV_ISBESTMODE, "true");
+        getHdmiData(&data);
+        getHdmiOutputMode((char *)outputmode, &data);
+    } else {
+        SYS_LOGI("outputmode is not auto\n");
+        setBootEnv(UBOOTENV_ISBESTMODE, "false");
+    }
 
     //1. get hdmi data
     mHdmidata.state = OUPUT_MODE_STATE_SWITCH;
@@ -1009,36 +1035,6 @@ void DisplayMode::setSourceOutputMode(const char* outputmode, output_mode_state
     bool cvbsMode = false;
     char tmpMode[MODE_LEN] = {0};
 
-    //Vas added to control HDMI output
-    if (!strcmp(outputmode, "displayon")) {
-        if (isDisplayOn == true) return;
-        pSysWrite->writeSysfs(DISPLAY_HDMI_STOP_HPD, "0");
-        isDisplayOn = true;
-        return;
-    } else if (!strcmp(outputmode, "displayoff")) {
-        if (isDisplayOn == false) return;
-        pSysWrite->writeSysfs(DISPLAY_HDMI_PHY, "0");
-        usleep(50000);
-        pSysWrite->writeSysfs(DISPLAY_HDMI_STOP_HPD, "1");
-        usleep(50000);
-        isDisplayOn = false;
-        return;
-    }
-
-    // When user switch outputmode, store bestmode
-    if (OUPUT_MODE_STATE_SWITCH == state) {
-        if (!strcmp(outputmode, "auto")) {
-            hdmi_data_t data;
-
-            SYS_LOGI("outputmode is [auto] mode, need find the best mode\n");
-            setBootEnv(UBOOTENV_ISBESTMODE, "true");
-            getHdmiData(&data);
-            getHdmiOutputMode((char *)outputmode, &data);
-        } else {
-            SYS_LOGI("outputmode is not auto\n");
-            setBootEnv(UBOOTENV_ISBESTMODE, "false");
-        }
-    }
 
     bool deepColorEnabled = pSysWrite->getPropertyBoolean(PROP_DEEPCOLOR, true);
     pSysWrite->readSysfs(HDMI_TX_FRAMRATE_POLICY, value);
@@ -1155,24 +1151,6 @@ void DisplayMode::setSourceOutputMode(const char* outputmode, output_mode_state
             }
         } else {
             initHdrSdrMode();
-            char hdrmode[MODE_LEN] = {0};
-            pSysWrite->getPropertyString("persist.vendor.sys.hdrmode", hdrmode, "0");
-            if (strstr(hdrmode, "0")) // hdr off
-            {
-                pSysWrite->writeSysfs(HDR_FORCE_OUTPUT, HDR_FORCE_OUTPUT_ON);
-                pSysWrite->writeSysfs(HDR_POLICY, HDR_POLICY_DISABLE);
-                SYS_LOGI("hdrmode off\n");
-            }else if (strstr(hdrmode, "1")) // hdr on (sink)
-            {
-                pSysWrite->writeSysfs(HDR_FORCE_OUTPUT, HDR_FORCE_OUTPUT_OFF);
-                pSysWrite->writeSysfs(HDR_POLICY, HDR_POLICY_SINK);
-                SYS_LOGI("hdrmode from sink\n");
-            }else if (strstr(hdrmode, "2")) // hdr on (source)
-            {
-                pSysWrite->writeSysfs(HDR_FORCE_OUTPUT, HDR_FORCE_OUTPUT_OFF);
-                pSysWrite->writeSysfs(HDR_POLICY, HDR_POLICY_SOURCE);
-                SYS_LOGI("hdrmode from source\n");
-            }
         }
     }
 
@@ -3403,6 +3381,22 @@ void DisplayMode::initHdrSdrMode() {
         pSysWrite->getPropertyString(PROP_SDR_MODE_STATE, mode, flag ? SDR_MODE_AUTO : SDR_MODE_OFF);
     }
     setSdrMode(mode);
+
+    char hdrmode[MODE_LEN] = {0};
+    pSysWrite->getPropertyString("persist.vendor.sys.hdrmode", hdrmode, "0");
+    if (strstr(hdrmode, "0")) {// hdr off
+        pSysWrite->writeSysfs(HDR_FORCE_OUTPUT, HDR_FORCE_OUTPUT_ON);
+        pSysWrite->writeSysfs(HDR_POLICY, HDR_POLICY_DISABLE);
+        SYS_LOGI("hdrmode off\n");
+    } else if (strstr(hdrmode, "1")) {// hdr on (sink)
+        pSysWrite->writeSysfs(HDR_FORCE_OUTPUT, HDR_FORCE_OUTPUT_OFF);
+        pSysWrite->writeSysfs(HDR_POLICY, HDR_POLICY_SINK);
+        SYS_LOGI("hdrmode from sink\n");
+    } else if (strstr(hdrmode, "2")) {// hdr on (source)
+        pSysWrite->writeSysfs(HDR_FORCE_OUTPUT, HDR_FORCE_OUTPUT_OFF);
+        pSysWrite->writeSysfs(HDR_POLICY, HDR_POLICY_SOURCE);
+        SYS_LOGI("hdrmode from source\n");
+    }
 }
 
 int DisplayMode::modeToIndex(const char *mode) {
diff.patch (5,153 bytes)   

(SW) Jerry Lin

2023-09-11 22:42

developer   ~0014131

Hi YK,
I update test FW to ALT Server.

link: /release_by_fxn/smart3_test/Mantis1806/usb_bfx-at100_V15.537.65.zip

Jerry

(SW) Jason Ling

2023-09-20 10:10

developer   ~0014176

Hi YK,

This ticket has been resolved.

2023-09-12 17:40:55 | jason.tf.ling@fii-.. | fbb145b | vendor/amlogic/common | [BPM-22395] re-setting color space when changing resolution
2023-09-11 19:26:17 | peterch.ch.chen@ma.. | 86a4a21 | vendor/amlogic/common | Merge remote-tracking branch 'remotes/skb-amandroids/AML_AT
2023-09-11 12:07:52 | Sh.Yu@amlogic.com | 6a0d27e | vendor/amlogic/common | Revert "Systemcontrol: color space be changed after switch
2023-09-05 16:03:20 | liang-chyi.lin@fii.. | 7e8924c | vendor/amlogic/common | [BPM-22284] Revert "corrected the method of HDMI enable/di
2023-09-05 15:25:24 | jason.tf.ling@fii-.. | ca9f9e3 | vendor/amlogic/common | [NO-JIRA] Remove duplicate code

Thanks,
Jason

(ALTech) Younkwang Jung

2023-09-20 10:38

developer   ~0014179

Hi Jason

There's still a minor issue left
https://jira.skbroadband.com/browse/BPM-22383
I'll review it more by tomorrow and let you know

Thanks
YK.Jung

(ALTech) JunGyu Kim

2023-09-21 12:46

developer   ~0014185

Hi Jason,

The other issues currently occurring in the latest code.
It has been confirmed that this is an issue that occurs because specific TVs follow different routines.

Therefore, it would be better to use 0912.patch, which contains Intek's solution previously shared through wechat.
Therefore, please proceed as follows.

1. Revert the commit below
2023-09-12 17:40:55 | jason.tf.ling@fii-.. | fbb145b | vendor/amlogic/common | [BPM-22395] re-setting color space when changing resolution

2. Apply 0912.patch
Please use BPM-22441 jira ticket when commit.

When finish, please share the test FW for ND/SD.

Thank you.
Kim

(SW) Jason Ling

2023-09-21 15:35

developer   ~0014188

Hi JunGyu,

2023-09-21 14:11:51 | jason.tf.ling@fii-.. | a864298 | vendor/amlogic/common | [BPM-22441] Fixed an issue the colorspace value was set to
2023-09-21 14:03:29 | jason.tf.ling@fii-.. | 8823530 | vendor/amlogic/common | Revert "systemcontrol: set isbestmode to false when manual

image file
/release_by_fxn/tmp/mantis1806

Thanks,
Jason

(ALTech) JunGyu Kim

2023-09-21 19:21

developer   ~0014191

Hi Jason.

I have tested your test FW, there is an issue.
1. Set resolution to 2160p
2. Remove HDMI Cable
3. Connect HDMI Cable
4. Verify resolution and color space ==>> resolution was set to 1080p and color space is 422,8bit in specific TV.

We have checked the log and we found below patch affect this issue.
=======================================================================================
commit 46b263a85e3461152c26aee84e358ba9f697aa9c
Author: SungHwan Yu <Sh.Yu@amlogic.com>
Date: Tue Sep 12 13:45:39 2023 +0900

    Revert "Revert "Systemcontrol: color space be changed after switch resolution [1/1]""

    This reverts commit 6a0d27e6db26624980aa5c37ac22ccf782ac0325.
=======================================================================================

Please remove this commit.

Thank you.
Kim

(SW) Jason Ling

2023-09-21 20:06

developer   ~0014192

Hi JunGyu,

2023-09-21 19:28:27 | jason.tf.ling@fii-.. | dd74270 | vendor/amlogic/common | Revert "Revert "Revert "Systemcontrol: color space be chan

/release_by_fxn/tmp/mantis1806/691a

Thanks,
Jason

(ALTech) JunGyu Kim

2023-10-12 12:47

developer   ~0014276

Hi Jason,

We found same issue on SAMSUNG TV.
The issue details are as follows.
1. Sleep -> Wake up with the resolution selected "auto", the resolution changes to 1080p.
2. Remove the HDMI cable and inserted with the resolution selected "auto", the resolution changes to 1080p.

The menu names are different for each SAMSUNG TV, but on the TVs we own, an issue occurs when the items below are disabled.
Setting -> General -> External Device Manager -> HDMI UHD Color -> Disable connected HDMI number

After checking the log, we confirmed that the resolution was changed due to the routine below.
========================================================================================================================================
10-06 10:49:10.163 3416 3463 I SystemControl: [/SysWrite.cpp, writeSys, 242] write /sys/class/amhdmitx/amhdmitx0/valid_mode, val:2160p60hz422,12bit end
10-06 10:49:10.165 3416 3463 I SystemControl: [/SysWrite.cpp, writeSys, 242] write /sys/class/amhdmitx/amhdmitx0/valid_mode, val:2160p50hz422,12bit end
10-06 10:49:10.167 3416 3463 I SystemControl: [/SceneProcess.cpp, isSupport4KHDR, 1062] isSupport4KHDR 4k hdr not support
10-06 10:49:10.167 3416 3463 I SystemControl: [/SysWrite.cpp, writeSys, 242] write /sys/class/amhdmitx/amhdmitx0/valid_mode, val:1080p60hz422,12bit end
10-06 10:49:10.167 3416 3463 I SystemControl: [/SceneProcess.cpp, isSupportnon4KHDR, 1093] isSupportnon4KHDR mode:[1080p60hz], deep color:[422,12bit]
========================================================================================================================================


Therefore, the issue appears to be fixed when modified as follows.
========================================================================================================================================
/a12_smart3/vendor/amlogic/common$ git diff .
diff --git a/frameworks/services/systemcontrol/SceneProcess.cpp b/frameworks/services/systemcontrol/SceneProcess.cpp
index 1e647b6..4e848cf 100755
--- a/frameworks/services/systemcontrol/SceneProcess.cpp
+++ b/frameworks/services/systemcontrol/SceneProcess.cpp
@@ -300,6 +300,7 @@ static const char* HDR_NON4K_COLOR_ATTRIBUTE_LIST[] = {

  //this is prior selected list of HDR 4k colorspace(2160p60hz/2160p50hz)
  static const char* HDR_4K_COLOR_ATTRIBUTE_LIST[] = {
+ COLOR_YCBCR420_8BIT,
      COLOR_YCBCR420_10BIT,
      COLOR_YCBCR422_12BIT,
  };
========================================================================================================================================

Please check if this symptom occurs on the SAMSUNG TV owned by FXN.
If an issue occurs, please apply the above modification and verify the issue is resolved.

Additionally, a video reproducing the issue has been attached. (15.537.68)
On this TV, disable "HDMI UHD Color" on TV, the issue was occurred.

Thank you.
Kim

(ALTech) JunGyu Kim

2023-10-12 12:48

developer   ~0014277

(SW) Jason Ling

2023-10-12 17:12

developer   ~0014284

Hi JunGyu,

I can not reproduce your issue with our Samsung TV.
I also checked the menu with our Samsung TV, we don't have "HDMI UHD Color" item

Please refer to Fii_SamsungTV.jpg

Thanks,
Jason
Fii_SamsungTV.jpg (278,621 bytes)

(ALTech) JunGyu Kim

2023-10-12 17:39

developer   ~0014286

Hi Jason,

Looking at the image you provided, I think "Input Signal Plus" will have the same function.
When I visited Samsung and tested several TVs, I found that the names of the menus were different for each TV.
Could you please test through "Input Signal Plus" menu?

Thank you.
Kim

(SW) Jason Ling

2023-10-12 18:00

developer   ~0014289

Hi JunGyu,

I checked "Input Signal Plus", but we still can not reproduce it on our side.

Thanks,
Jason

(SW) Jason Ling

2023-10-13 11:11

developer   ~0014296

Hi JunGyu,

According to the following test steps, I can reproduce it this morning.

1. As shown in the video, check if the TV resolution is 2160p (STB is auto) with “Input Signal Plus” enabled, then disable “Input Signal Plus” and check the resolution changes to 1080p.

the TV Resolution in this time is always 1080, we need to change STB Resolution to 2160 then change back to auto, the TV resolution will be 2160

2. With “Input Signal Plus” disabled, check if the TV resolution is 2160p, then Sleep -> Wake up and check the TV resolution changes to 1080p.
3. With “Input Signal Plus” disabled, check if the TV resolution is 2160p, then remove the HDMI cable and insert it and check the TV resolution changes to 1080p.

After applying your patch, the issue is gone.

Thanks,
Jason

(ALTech) JunGyu Kim

2023-10-13 12:15

developer   ~0014299

Hi Jason,

Thank you for verification.
If there are no problems with the patch above, please commit it.
Please use BPM-22982 ticket when commit it.
https://jira.skbroadband.com/browse/BPM-22982

Please use below comment.
"Fixed issue the resolution changes to 1080p when Input Signal Plus function is disabled on Samsung TV"
If you have a better comment, feel free to use it.

Thank you.
Kim

(SW) Jason Ling

2023-10-13 13:37

developer   ~0014300

Hi JunGyu,

Done,

2023-10-13 13:34:27 | jason.tf.ling@fii-.. | c4388c8 | vendor/amlogic/common | [BPM-22982] Fixed issue the resolution changes to 1080p wh

Thanks,
Jason

(ALTech) Younkwang Jung

2024-07-09 09:59

developer   ~0016218

Hi Jason

Thank you for your support
I will close this ticket

YK.Jung

Issue History

Date Modified Username Field Change
2023-09-04 20:06 (ALTech) Younkwang Jung New Issue
2023-09-04 20:06 (ALTech) Younkwang Jung Status new => assigned
2023-09-04 20:06 (ALTech) Younkwang Jung Assigned To => (SW) Kerwin Chen
2023-09-04 20:06 (ALTech) Younkwang Jung File Added: logcat.zip
2023-09-04 20:06 (ALTech) Younkwang Jung File Added: KakaoTalk_20230904_204921654.mp4
2023-09-04 20:07 (ALTech) Younkwang Jung Issue Monitored: (ALTech) SY Yoon
2023-09-04 20:07 (ALTech) Younkwang Jung Issue Monitored: (ALTech) JunGyu Kim
2023-09-04 20:32 (ALTech) JunGyu Kim Note Added: 0014074
2023-09-04 20:38 (ALTech) JunGyu Kim Note Added: 0014075
2023-09-04 21:17 (SW) Kerwin Chen Assigned To (SW) Kerwin Chen => (SW) Jason Ling
2023-09-04 21:17 (SW) Jason Ling Note Added: 0014076
2023-09-04 21:40 (SW) Jason Ling Note Added: 0014077
2023-09-04 21:40 (SW) Jason Ling File Added: image-3.png
2023-09-05 16:15 (SW) Jason Ling Assigned To (SW) Jason Ling => (SW) Jerry Lin
2023-09-05 16:17 (SW) Jerry Lin Note Added: 0014079
2023-09-07 18:01 (ALTech) Younkwang Jung Note Added: 0014108
2023-09-07 18:01 (ALTech) Younkwang Jung File Added: LGTV_2160P_Flicker_48s.mp4
2023-09-07 18:01 (ALTech) Younkwang Jung File Added: LGTV_2160P_Flicker_14h23m_logcat (1).log
2023-09-07 18:03 (ALTech) Younkwang Jung Note Edited: 0014108 View Revisions
2023-09-07 19:42 (ALTech) JunGyu Kim Note Added: 0014109
2023-09-08 17:11 (SW) Jerry Lin Note Added: 0014112
2023-09-08 17:13 (SW) Jerry Lin Note Edited: 0014112
2023-09-08 17:46 (SW) Jerry Lin Note Added: 0014113
2023-09-08 21:23 (SW) Jerry Lin Note Edited: 0014113
2023-09-11 10:16 (ALTech) Wooshin Kang Note Added: 0014116
2023-09-11 10:24 (SW) Jerry Lin Note Added: 0014118
2023-09-11 10:50 (ALTech) Wooshin Kang Note Added: 0014119
2023-09-11 10:51 (ALTech) Wooshin Kang Note Edited: 0014119
2023-09-11 11:03 (SW) Jerry Lin Note Added: 0014121
2023-09-11 11:05 (SW) Jerry Lin Note Added: 0014122
2023-09-11 11:42 (ALTech) Wooshin Kang Note Added: 0014123
2023-09-11 12:13 (SW) Jason Ling Note Added: 0014124
2023-09-11 15:25 (SW) Jerry Lin Note Added: 0014126
2023-09-11 15:26 (SW) Jerry Lin Note Edited: 0014126
2023-09-11 22:13 (SW) Jerry Lin Note Added: 0014130
2023-09-11 22:13 (SW) Jerry Lin File Added: diff.patch
2023-09-11 22:42 (SW) Jerry Lin Note Added: 0014131
2023-09-20 10:10 (SW) Jason Ling Assigned To (SW) Jerry Lin => (ALTech) Younkwang Jung
2023-09-20 10:10 (SW) Jason Ling Status assigned => resolved
2023-09-20 10:10 (SW) Jason Ling Resolution open => fixed
2023-09-20 10:10 (SW) Jason Ling Note Added: 0014176
2023-09-20 10:38 (ALTech) Younkwang Jung Note Added: 0014179
2023-09-21 12:46 (ALTech) JunGyu Kim Note Added: 0014185
2023-09-21 15:35 (SW) Jason Ling Note Added: 0014188
2023-09-21 19:21 (ALTech) JunGyu Kim Note Added: 0014191
2023-09-21 20:06 (SW) Jason Ling Note Added: 0014192
2023-10-12 12:47 (ALTech) JunGyu Kim Status resolved => feedback
2023-10-12 12:47 (ALTech) JunGyu Kim Resolution fixed => reopened
2023-10-12 12:47 (ALTech) JunGyu Kim Note Added: 0014276
2023-10-12 12:47 (ALTech) JunGyu Kim Assigned To (ALTech) Younkwang Jung => (SW) Jason Ling
2023-10-12 12:48 (ALTech) JunGyu Kim Note Added: 0014277
2023-10-12 12:48 (ALTech) JunGyu Kim File Added: KakaoTalk_20231012_134553828.mp4
2023-10-12 17:12 (SW) Jason Ling Note Added: 0014284
2023-10-12 17:12 (SW) Jason Ling File Added: Fii_SamsungTV.jpg
2023-10-12 17:39 (ALTech) JunGyu Kim Note Added: 0014286
2023-10-12 18:00 (SW) Jason Ling Note Added: 0014289
2023-10-13 11:11 (SW) Jason Ling Note Added: 0014296
2023-10-13 12:15 (ALTech) JunGyu Kim Note Added: 0014299
2023-10-13 13:37 (SW) Jason Ling Assigned To (SW) Jason Ling => (ALTech) JunGyu Kim
2023-10-13 13:37 (SW) Jason Ling Status feedback => resolved
2023-10-13 13:37 (SW) Jason Ling Resolution reopened => fixed
2023-10-13 13:37 (SW) Jason Ling Note Added: 0014300
2024-07-09 09:59 (ALTech) Younkwang Jung Note Added: 0016218
2024-07-09 09:59 (ALTech) Younkwang Jung Status resolved => closed